This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
RE: Do you have multiple IPs on the server? ~Lorraine Nimfreetexynds 17.May.12 08:02 AM a Web browser Sametime Standard 8.5.2 IFR1Windows
Thanks for that.
As long as it's working
Thing is, it's working with blank entries whilst the instructions say to put something in there.... It's the putting a value in that breaks it
5.Under Server Connections, type the fully qualified Host Name and Port for the internal Sametime processes to communicate with one another.
Community Services listens for direct TCP/IP connections from Community Services of other Sametime Community Servers on this port. If you have installed multiple Sametime servers, this port must be open for presence, chat, and other data to pass between the servers.
6.Under Client Connections, type the fully qualified Host Name and Port from which Community Services listen for direct TCP/IP connections and HTTP-tunneled connections from the Community Services clients.
A direct TCP/IP connection occurs when the Sametime client uses a unique Sametime protocol over TCP/IP to establish a connection with the Community Services.
7.Under HTTP Tunneled Client Connections, type the fully qualified Host Name and Port from which Community Services clients can make HTTP-tunneled connections to the Community Services multiplexer.
Community Services clients can make HTTP-tunneled connections on both ports 80 and 8082 by default. Port 8082 ensures compatibility with previous Sametime releases. In previous releases, Sametime clients made HTTP-tunneled connections to the Community Services only on port 8082. If a Sametime Connect client from a previous Sametime release attempts an HTTP-tunneled connection to a Sametime server, the client might attempt this connection on port 8082.